Fix locale-dependent JSON float parsing (Issue #241) #255
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR syncs a commit ported from an upstream fork into this repo to fix locale-dependent JSON float parsing.
Original commit
strtod()usage when parsing JSON numeric tokens with a locale-independentstrtod_c()implementation, ensuring JSON floats are always parsed using.as the decimal separator (per JSON spec).Why it fits this repo’s guidelines/policies
.as the decimal separator; parsing should not vary based onLC_NUMERIC.strtod_l()/ global locale switching, which can be inconsistent across platforms and tricky for thread-safety.Notes (if any adaptations):
Why it’s useful here
Clocales (e.g. French/German).Testing
uv sync --directory tests(pass)make test-loadable python=./tests/.venv/bin/python(pass)Cnumeric locale and verifies JSON float parsing remains correct.